TPUG - Toronto PET Users Group/TPUG Users Group CD/TPUG Users Group CD.iso/AMIGA/AMICUS/AMICUS05.ADF/text/v1.1update

Text File | 1986-01-15 | 35KB | 834 lines

The following files comprise the V1.1 support notes being supplied
with your developer's update kits. The original notes are extensive
and not in any particular order. For your convenience, the support
notes have been broken into five files (messages). These files and
their sizes are detailed below:

   1. Support1.1   (9199 bytes) -- general notes, memory
         considerations, Dos/Cli , preferences, 680x0 support.

   2. Exec1.1      (8812 bytes) -- Workbench, Rom info, Libraries
         Sprites, Miscellaneous hardware info.

   3. Intuition1.1 (6308 bytes)-- new features, cautions, etc.

   4. Devices1.1   (3676 bytes) -- printer, serial, audio, clipboard.

   5. Utilities1.1 (6308 bytes) -- Alink, ATOM, StripA, objdump,
     speech, assembler notes, notepad-calculator, other software
     notes, icon-editor, ED, demos


===SUPPORT1.1===    25 November 1985

New Features in Amiga System Software Release 1.1

General Notes:
--------------
When using Release 1.1, the system taken as a whole is much more
reliable.  Because the release includes so many improvements, the
1.1 software should always be used as soon as it is available.

The system software in Release 1.1 uses 3K bytes more memory
than Release 1.0.

When the first system requester is displayed, 192 bytes of memory
are permanently allocated.

The system clock is much more accurate in Release 1.1 than it
was in Release 1.0.  The new clock is accurate to within a few seconds
per day.

When using Release 1.1 of the system software, the date and time
can no longer be set by poking a system memory location.  There are
now three ways to change the date and time:

     with Preferences

     by entering the AmigaDOS DATE command

     from within a program, by using the timer device TR_SETSYSTIME
     command defined in the timer.h and timer.i include files

The window for the Clock tool is not automatically selected when
the Clock is opened.  This is not a bug; it may, however,
confuse people.


Memory
------
Memory remains allocated for diskloaded software such as
the printer devices until their usage count goes to zero and another
program performs an AllocMem() requiring the memory.  This is done
intentionally to reduce reloading of software from the disk.  Some
programs that enquire as to available memory without doing an AllocMem()
may be tricked into thinking that there is insufficient memory for
them to run.

If there is little available memory, you may generate an alert
by:
     opening or setting up a menu (results in Guru Meditation Number
     4010 0000)

     rendering text (The Guru Meditation Number for this alert is
     2010009.)

     opening 1.0 demonstrations or other programs that do not handle
     outofmemory errors returned by the system software.  (This is
     much less likely to occur when using the 1.1 system software
     than it was when using 1.0 system software.)

If there is little memory available and an attempt to move a
window fails, memory may be lost.

Some programs allow windows that can be narrower than 16 pixels
across.  If such a window contains a sizing gadget, resizing it so
that it is narrower than 16 pixels across can corrupt memory.

You can cause the system to crash due to lack of memory by putting
too much in the RAM disk.  In particular, copy df0: to ram: all"
will likely cause the system to fail when the system fills up all
its free memory with files.


Dos/Cli
-------
The 1.0 CLI INFO command will not correctly display the name
field for the RAM disk (ram:) when used with the 1.1 Kickstart disk.

The message for AmigaDOS error 218 has changed.  In Release 1.0,
the message was Device not mounted"; in Release 1.1, the message
is Device (or volume) not mounted".

The CLI command DISKCOPY should not be used from within a command
file if the disk being copied is the SYS: disk.  This is because the
EXECUTE command may need to write to SYS:

Entering the AmigaDOS CD command without arguments will not always
display the name of the current directory.  If you enter CD with the
name of an assign as its argument (for example, CD devs:), then try
to use CD to return to the root directory (by entering CD :), entering
CD without arguments returns the name of the last assign you included
as an argument to CD.

Issuing the AmigaDOS ENDCLI command from within an AmigaDOS command
file can leave the command file locked.  Because the startup command
file includes an ENDCLI command, the file startup-sequence can become
locked.

Each time a nonCLI process (that is, a process created by
a call to CreateProc()) calls the AmigaDOS EXECUTE function, approximately
50 bytes of memory are lost plus one byte of memory is lost for each
character in the argument to EXECUTE.

In Release 1.0, the WaitForChar() function returned a character
the next time a key was pressed.  In Release 1.1, the function now
returns a character immediately if one has been buffered.

The CLI commands C:LAB and C:ENDIF no longer return errors when
used in command files.

Typing very rapidly when a CLI window is selected and
in the process typing CTRLX may cause an alert.

When using the CLI or any of its commands, entering AmigaDOS
file or directory descriptions (pathnames") containing 100 or
more characters will cause a software failure.  While AmigaDOS's limit
for total number of characters in a pathname is 255 (with not more
than 30 characters in each component) the maximum number of characters
that can safely be included in a pathname when entered as part of
CLI command varies.  To be safe, pathnames should contain no more
than 60 characters.

If there are more than 10 levels of AmigaDOS directories, AmigaDOS
will fail if the DIR <directory-name> OPT A command is entered.  This
failure is due to insufficient stack space.  Running out of stack
space in this instance can be avoided if the stack space is increased;
doubling the default stack size by entering the STACK 8000 command
will allow at least 20 levels of directories.

Entering the following sequence of AmigaDOS commands will corrupt
memory:

   MAKEDIR 111111111111111111111111111111
   CD 111111111111111111111111111111
   MAKEDIR 222222222222222222222222222222
   CD 222222222222222222222222222222
   MAKEDIR 333333333333333333333333333333
   CD 333333333333333333333333333333

The prompt becomes:

   858993459>

If the CD command is entered now, it gives the following result:

     df0:111111111111111111111111111111/222222222222
     222222222222222222/33333333333333333yyyy333333333

in which the y's have umlauts.


If the following sequence of AmigaDOS commands is entered 49
times in a row by means of an command file, memory is corrupted in
the same way as the previous example:
    MAKEDIR x
    CD x

If DELETE :x ALL is entered after this, AmigaDOS will fail unless
the stack size has been increased.

The AmigaDOS Lock(nil:") routine asks the user to insert
volume NIL:".

The output for the AmigaDOS LIST command is not aligned for file
names containing 30 characters.

The AmigaDOS CreateProcess() routine does not copy the new process
name.

You cannot rename a file or icon if the only change in the new
name is in the capitalization of letters.  Do the rename as a twostage
process.

Preferences:
-------------
Preferences may not appear to be working if there are a number
of other tools open at the same time.  It's just running slowly.

In Preferences, the printer file: generic, is the default file when
Custom specified for the Printer setting. Selecting generic allows the
printing of plain text (that is, text without added escape sequences
for special characters, different type styles, etc.) on most printers.

Preferences now checks to see that the settings for paper margin
and paper length are at least 1 and that the right margin setting
is larger than the left margin setting.

When using the 1.0 release of Preferences with the 1.1 Kickstart
disk, there are certain features that are not available:
     The date and time cannot be set, nor can they be displayed.

     The HewlettPackard LaserJett and LaserJet Plust printers cannot
     be used. These LaserJet and LaserJet Plus items are not displayed
     properly in Preferences.


Under certain circumstances, vigorously dragging the Display
Centering Gadget in Preferences will cause false images to appear
below the Pointer.  These images do no harm, and disappear immediately.


680xx Support
--------------
With the exception of the Calculator, software in the 1.1 release
is compatible with the 68010 and the 68020 processors.

To maintain compatiblity with the Motorola MC68010 and MC68020
microprocessors, GetCC() should now be used to get the processorr
condition codes.  GetCC() handles the differences between the processors
such as the fact that MoveSR is an invalid user mode operation in
the 68010 and 68020.

It is no longer possible to use InitStruct() to initialize the APTR
field.  Attempting to intialize the APTR field causes an alert.
LONG fields should now be used in place of APTR fields.

Programmers should be sure NOT to use the upper 8 bits of a pointer for
storing unrelated information, since the 68020 uses all 32 bits for
addressing.

For those doing systems work, Exec maintains flags in the AttnFlags field
of ExecBase which describe the type of processor in your machine.  Exec's
coldstart procedure will update certain library entry vectors as necessary
to maintain compatability.  If you write code that uses the Supervisor()
function, keep in mind that your stack frame is processor dependent.  Use
the SuperState() function for processor independent supervisor mode entry.

V1.1 ROMWack will correctly display information for 68010/20 address and
bus errors.

When the 68020 is detected during coldstart, its instruction cache is
enabled.  This has implications for programmers writing self-modifying
code.

Other Hardware
--------------
Hardware manual, page 8-4:  The maximum mouse speed is incorrect.
The correct maximum speed is 38 inches per second.


===SYSTEM/EXEC===

Workbench
----------
A program that is listening to a requester cannot refresh its
windows.  In particular, when Workbench is listening to a system requester
such as a requester asking for a new disk, moving the requester or
any Workbench windows will leave portions of the Workbench windows
undrawn.  This will correct itself when the requester terminates.

In a 256K, onedrive system, the requester that appears when
you copy disks by dragging one icon over another on the Workbench
has the following problem:  the text within the gadgets is too large
for the gadgets, so that instead of the entire word Continue appearing
in the gadget, only part of the word appears.

When using Extended Selection on the Workbench, selecting an
area between icons with the Shift key held down no longer causes already
selected icons to be deselected.

Amiga has adopted the Lattice C conventions for determining whether
a program is running under the Workbench and for receiving parameters
from either the Workbench or the CLI.  We now encourage all developers
to use these conventions.  Support for the Lattice conventions is
in the startup routine that comes with the Lattice libraries.  Amiga
will provide a new startup routine for those who do not use Lattice
highlevel I/O.

The default screen title for the Workbench screen is now:

    Workbench Screen

For an application whose window(s) appear in the Workbench
screen, we recommend that ScreenTitle in its Window structures include
a title that identifies the application.

Attempting to open the Initialize tool directly (that is, either
by selecting the Initialize icon in the System drawer on the Workbench
disk, then choosing Open from the Workbench menu or by pointing to
the Initialize icon and doubleclicking the Selection button)
causes a requester to be displayed.  The message in the requester
states that the Initialize menu item is in the Workbench menu when,
in fact, it is in the Disk menu.

In the requester that appears after choosing Info from the Workbench
menu, selecting one gadget then quickly selecting another gadget can
corrupt the display.

On the Workbench, if a drawer is duplicated, then immediately
thereafter the same drawer is duplicated, there will be two new icons
labeled copy of <drawername>".  Because the file system
is not equipped to deal with two directories or files with the same
name in a given drawer, this causes problems.  Note that the disk
is not damaged  only Workbench get confused.

An attempt to use Extended Selection to specify an argument to
a tool when a Workbench drawer is first opened will in most cases
fail.  (Using Extended Selection to a specify a tool's argument(s)
works as follows:  the tool's icon is selected, the Shift key is held
down, the icon(s) for the argument file(s) is(are) selected, then
the Shift key is released.)  A second attempt will most often succeed.

If a disk's drawer is opened on the Workbench, an icon within
the disk drawer selected, the Shift key held down, the icon for the
disk selected, then an attempt is made (with the Shift key still held
down) to drag the icon that was first selected in the disk drawer,
additional copies of the disk icon appear in new positions.  Choosing
Redraw twice from the Special menu restores the screen.

If you select a disk icon and then choose rename while that disk
is not in a drive, Workbench will get confused.  If there is ANOTHER
disk in the drive, Workbench typically ignores the attempted renameperhaps
closing down the open window for the  missing disk that was causing
its icon to be left on the Workbench screen.  If there is NO disk
in the drive, Workbench reports that fact in a requester.  If at that
point you give Workbench the proper disk, everything works.  If you
give Workbench a different disk, Workbench will crash.

Workbench changes the Pointer to the Wait Pointer whenever it
is not listening to you.  For instance, if you've selected a gadget
in the requester that appears when you choose Rename and then click
outside that gadget, the Wait Pointer will appear.  This means that
you should click in the Rename requester again.

When you choose Version from the Workbench Special menu, the
screen will flash once.  This can be safely ignored.

Rom Kernal -- general
---------------------
Graphics Kernel routines are now much more reliable when memory
is low.

Use of the graphics InitLayer() routine is discouraged.  To use
the layer library without Intuition, use NewLayerInfo() and DisposeLayerInfo().

The new Exec function TypeOfMem() should be used by programs wishing
to know whether a given address is in Chip memory or Fast memory.
This function will insure compatability with future Amiga architectures.
It should be used instead of assuming that certain fixed address boundaries
define the break between Chip and Fast memory.

When using Release 1.1 of the system software, layer operations
are consistently slower if many windows are open.  This is due to
more extensive outofmemory checking.  Note that layer operations
are faster than in Release 1.0 when there are only a normal number
of windows open.

The '.', '-', and ENTER keys on the Amiga's numeric keypad have
the input event qualifier NUMERIC set in Release 1.1.


Libraries
---------
There is a new library on the Workbench disk, version.library,
that contains the current version and release numbers for the Workbench.
For the 1.1 release of Workbench, the version number is 1 and the
release number is 1.

The version checking for the routine OpenLibrary is in effect
in Release 1.1.  If getting a particular version of a library does
not matter, the Version parameter should be a 0.  To specify a library
from the 1.1 system software, the Version parameter should be 31.
(The version number for the current version is defined by LIBRARY_VERSION
in exec/types.h.

The OpenLibrary vector from Release 1.0 has been renamed OldOpenLibrary().
This allows programs compiled under Release 1.0 to run under Release 1.1.
Programs running under Release 1.1 should use the 1.1 OpenLibrary() vector.


Sprites
-------
SimpleSprites now support attached mode.  You first call GetSprite
for both sprites, call ChangeSprite to set up the correct data for
the sprites, then set the Attach bit for the oddnumbered sprite.
When you then call MoveSprite for the evennumbered sprite, both
sprites move.  Calling MoveSprite for the oddnumbered sprite
will not move the evennumbered sprite.

The problem of collisions being detected at BOB borders rather
than at the borders of the image within the BOB has been fixed in
Release 1.1

When using simple sprites, the last two words of the simple sprite
data structure must be initialized to 0,0 or FFFF, FF7F (0, 0 are
the preferred values).  Otherwise the sprite Attach bit will cause
problems for the sprite allocators.


Math
----
The Motorola Fast Floating Point (FFP) libraries are 20-25% faster
in Release 1.1 than in Release 1.0 and incorporate the latest bug
fixes from Motorola.

There is now a shared library on the Workbench disk
(mathieeedoubbas.library) that contains doubleprecision IEEE routines for
addition, subtraction, multiplication, and division as well as other basic
functions. (The Lattice IEEE transcendental functions are still in lc.lib
on the Lattice C disk.  All primitive mathffp functions are in
mathieeedoubbas.library)

In Release 1.0, the Motorola Fast Floating Point routines MFSPCmp
(Compare) and MFSPTst  (Test) did not work properly.  In Release 1.1,
these routines do work; however, they do not return the values documented
in Revision 1.0 of the Amiga ROM Kernel Manual.  The routines
now return a value of -1 if the first argument is less than the second;
0 if the arguments are equal; 1 if the first argument is greater than
the second.

Three new functions have been added to mathtrans.library for
Release 1.1.  These functions are:

fnum1 = SPAsin(fnum2);
fnum1 = SPAcos(fnum2);
fnum1 = SPLog10(fnum2);

These functions return the arcsine, arccosine and base 10 logarithm
of an FFP number.  Their usage is identical to the other similar single
argument functions in mathtrans.library such as SPAtan() and SPLog().
The standard assembly language entry points (_LVOSPAsin, _LVOSPACos
and _LVOSPLog10) for these three (3) new functions also exist.

Miscellaneous
-------------
If the BBUSY bit in register DMACONR is tested immediately after
blitting and there is heavy contention for chip" memory, the
bit may indicate that a blit has finished before it has even begun.
To be safe, the BBUSY bit must be tested twice.  Programmers should
use the graphics WaitBlit() function which handles this properly.


===INTUITION===

Intuition is now far more reliable than it was in Release 1.0.

Intuition destroys the minterms in the user's RastPort.  Programs
that set the minterms in the RastPort should set them again prior
to each rendering operation.

Intuition now uses the graphics library to move the Pointer;
it no longer moves the Pointer itself.

The files intuitionbase.h and intuitionbase.i now include declarations
for the initial portion of the Intuition library's internal structure.
For application programs, this structure is READ ONLY.  There are
two functions, LockIBase() and UnlockIBase(), that will be used in
the future to arbitrate access to these data.  These functions are
included in Release 1.1 for compatibility with future releases but
are not yet functional.  Information about the use of these functions
is included in the Intuition include files that will appear on the
new 1.1 Assembler and Lattice C disks.

In Release 1.1 each requester has its own layer.  Because of this:

     A requester is no longer cleared prior to each RefreshGadget()
     event.

     The appearance of requesters when they are being used is greatly
     improved.

     Programmers can no longer modify what appears in a requester by
     writing to the RastPort for the window in which the requester
     appears.

Problems may arise if a menu is being opened while Intuition
is changing state.  (Intuition most often changes state when it opens
or closes a window.)  When there is such a problem, it manifests itself
most often in display abnormalities such as partially highlighted
menu titles.  Only on rare occasions is the problem so severe that
resetting the Amiga is necessary.

Intuition has two new flags in the IDCMP field of the Window
structure:

VANILLAKEY

Set the VANILLAKEY flag in the IDCMPFlags field of your Window structure
to get a translation of each raw keycode RAWKEY event into the current
default character keymap of the Console Device.  In the USA, the default
keymap is the ASCII character set.  When you set this flag, you get
IntuiMessages in which the Code field has a character representing
the key that was struck on the keyboard.  This character is from the
default character KeyMap of the Console Device.  (For a brief discussion
of the Console Device, see page 5-17 of Intuition.)

INTUITICKS

Set the INTUITICKS flag in the IDCMPFlags field of your Window structure
if you want to receive timer events from Intuition when your window
is selected.  Intuition receives timer events approximately 10 times
a second.  In turn, a task whose INTUITICKS flag is set receives one
queuedup INTUITICKS message at a time.  If Intuition notices
that you have been sent an INTUITICKS message but you haven't replied
to the message, it does NOT send another message.  In some instances,
receiving these timer events from Intuition may make it unnessary
to open and directly manage the timer device.

In the include files for Intuition, a MENUTOGGLE feature appears.
This feature is not implemented.

When the Intuition AddGadget() function is called, RefreshGadgets()
must be called before the new gadgets will be displayed.

When a boolean gadget is rapidly and repeatedly selected while
it is being refreshed, its highlighting may get out of synchronization.
This problem appears in Graphicraft and in window gadgets; it also
appears, although less frequently, in window sizing gadgets.

Some programs may disable their menu by using the OffMenu() Intuition
function, as an alternative to the ClearMenuStrip() function.  Although
the menus will be successfully disabled, holding down the Menu mouse
button and rolling the Intuition pointer across the blank menu bar
will result in segments of the bar being highlighted as the mouse
passes over them. There are no other known side effects, and the display
will correct itself when the user releases the Menu button.

A warning about the Intuition MENUVERIFY, SIZEVERIFY, and REQVERIFY
IDCMP flags:  these flags should be set only if the rendering
of a screen is done through the screen's RastPort or there are other
compelling reasons to set the flags.   When any of these flags is
set, Intuition sends an IDCMP message to the application when the
appropriate event (menu button press, an attempt to size a window,
or the need to display a DoubleMenu Requester") occurs.
Because Intution blocks until it receives a reply to the IDCMP message,
if the application is suspended or for any other reason cannot respond
to the message, the system hangs.  Here is one example of the problem:

   When the MENUVERIFY flag is set for an application,
the menu button is pressed.  To signal the event, Intuition sends
an IDCMP message.  It then waits for a reply.  Before the application
replies, it makes a call to AmigaDOS that results in a error.  AmigaDOS
suspends the application while it attempts to post a system requester
which, in turn, requires the aid of Intuition.  Because both Intuition
and the application are now waiting for events that the other provides,
they are deadlocked.

    There are no easy solutions to this problem.  Short
of abandoning the use of the flags, the only approach is to prevent
the occurrence of the event (in the case of MENUVERIFY, by disabling
menus) whenever there is a risk that an application may not reply
to the IDCMP message that is sent to signal the event.

Please note these additions and corrections to revision 1.0 of
the manual Intuition:  The AMIGA User Interface:

     p. 2-10:  A depth entry of 2 in a NewScreen structure
results in 4 available colors, not 16.

     p. 5-17:  The first sentence in the second paragraph
should be replaced by the following:  String gadgets inherit
the font of the screen in which they appear.  For programs that use
the Workbench screen, this means that the font may change if the the
font setting in Preferences is changed.  If you wish to be informed
of changes in Preferences settings, set the NEWPREFS flag in the IDCMPFlags
field in your Window structure."

     p. 8-12:  All tasks for which the NEWPREFS flag is
set will receive messages informing them of changes, either by users
or other tasks, to Preferences.

     p. 8-12:  There are two new IDCMP event flags:



===PRINTERS and DEVICES===

Printer
-------
If a Reset command is issued directly to a printer through the
printer device, there must be a delay of at least one second before
any further commands are issued.

New Printer Control Files have been added for the HewlettPackard
LaserJet and LaserJet Plus laser printers.  At the same time, existing
Printer Control Files have been improved and made more reliable.

When using the HewlettPackard LaserJett and LaserJet
Plust printers with an Amiga, the Length setting for printer
paper in Preferences must be no greater that 62 for 8-1/2" X 11" paper.
The length setting in Textcraft must be no greater than 60.

When using Textcraft, the Spacing printer setting in Preferences
has no effect on the output from HewlettPackard LaserJett and
LaserJet Plust printers.  These printers can only print
6 lines per inch when used with Textcraft.

Serial
------
The Serial Device has been improved for Release 1.1.  It now
supports the RTS/CTS (7wire) flowcontrol protocol as well
as Quick_IO for reads.  In addition, it is far more reliable.

There is no Preferences setting for the serial device parameters
other than baud rate.  In particular, there is (currently) no easy
way for a user to specify that RTS/CTS (7wire) flow control should
be used for a serial printer.  The user would have to construct a
print program that sends parameter setting commands to the Exec serial
device.  A future version of Preferences and the serial device will
address this problem.

When using Release 1.0, linefeed characters sent to console.device
caused an advance to the next line, but no carriage return.  When
using Release 1.1, linefeeds sent to the Console Device are now expanded
by default to Carriage Return + Linefeed.  For linefeed characters
sent to the Console Device to be interpreted only as Linefeed,
not Carriage Return + Linefeed, the following must be sent to the
Console Device:

Control Sequence Introducer
     (either 9B hexidecimal or ESC-[)
followed by
     20l
(the digits 2, 0, and a lowercase letter l)

To resume the default expansion of linefeeds, the following must
be sent to the Console Device:

Control Sequence Introducer
     (either 9B hexidecimal or ESC-[)
followed by
     20h
(the digits 2, 0, and a lowercase letter h)

In Release 1.0, tab characters sent to console.device were converted
into spaces.  In Release 1.1, tab characters are interpreted according
to the current tab settings.  By default, tabs are set every eight
characters.

To set a tab, move to the desired position for the tab, then enter
either 88 hexidecimal or an ESCH character. To erase a particular tab,
move the position of the tab, then enter:

Control Sequence Introducer
     (either 9B hexidecimal or ESC-[ )
followed by
     g
(the lowercase letter g)

To clear all tabs, enter:

Control Sequence Introducer
     (either 9B hexidecimal or ESC-[ )
followed by
     3g
(the character '3' and a lowercase letter g)

Audio
-----
The audio device command ADCMD_ALLOCATE now works with the ADIOF_NOWAIT
flag cleared.  The CMD_WRITE command will not affect the volume and
periods registers if the ADIOF_PERVOL flag is cleared.

If a write to the audio device has been aborted and another write
command is issued a very short time afterward, the ADIO_PERVOL flags
in the I/O request block must be set for the new write.  If not, the
new data pointer (ioa_Data) and length (ioa_Length) may not be loaded.


Clipboard
---------
The Clipboard Device is faster and more reliable.  In addition,
the Clipboard Device now supports the Interchange File Format (IFF).
A specfication for IFF is included in the new Rom Kernal Manual.



===UTILTITIES===

Linker
------
A new system program loader lets you specify what kind of memory,Chip
or Fast, you want parts of a program (known as hunks) to be loaded into.
The loader is compatible with Release 1.0 software.

A new utility, ATOM, makes it possible to set flags to indicate
to the Loader what kind of memory a hunk should run in.  ATOM is used
before linking. If ATOM is used, the 1.1 ALINK, STRIPA, and OBJDUMP must
also be used.

ALINK, STRIPA, and OBJDUMP have been updated to work with ATOM.

Illegal hunk" messages will occur if an attempt is made to used
pre 1.1 releases of ALINK, STRIPA, or OBJDUMP on ATOMized files.

It is now possible to create overlays with ALINK.

The ALINK map display now displays names that include more than 8
characters.


Speech
------
There is now a SAY command on the CLI and Workbench disks.  This
command converts text to speech. The SAY command converts text to
synthesized speech.  You can enter text and commands interactively
or from a file.

To use SAY interactively, enter SAY at the CLI prompt.  Two windows
appear.  Enter text by selecting the Input window, then typing.  The
text is converted to speech when you press RETURN.  Phonemes for the
text that is converted appear in the Phoneme window.

There are a number of options you can select for SAY.  You can select
these options by typing them in when the Input window is selected,
then pressing RETURN.

OPTION    MEANING

-m             male voice
-f             female voice
-r             robot voice
-n             natural voice
-s##           speed [40-400]
-p##           pitch  [65-300]
-x <<filename> execute contents of filename

You can enter text and or command into a file, then execute the file
using the -x option.  You can also include text to be spoken and options
as parameters when entering the SAY command.

To quit, press RETURN without entering text.

Assembler
---------
The comment field for the NEXTNODE macro in the lists.i include
file has been changed to give the correct order for the parameters.

When running the Assembler with the -i option, a root directory
for a disk cannot be specified in the normal way, that is, by -i
df0:", -i df1:" or any specification that ends with a colon.
Instead, the normal name for the root must be followed by the name
of an existing subdirectory in the root, then a slash, as in this
example:

-i df0:mydir/

The reason for this is that the Assembler always expands directory
names specified in the -i option by adding a slash after the name
of the directory.  In the case of root directories, the resulting
colon followed by a slash, as in df0:/myfile", cannot be part
of a legal AmigaDOS file name.  When using the method shown above,
the expansion is instead df0:mydir//myfile", where the extra
slash added by the expansion after the subdirectory name has the meaning
go up one level in the directory hierarchy," in this case to
the root directory.

Notepad-Calculator
------------------
Notepad doesn't check that the file it is trying to open is actually
a Notepad note.

When using the Notepad with the Graphic option chosen for Print
As, if part of the Notepad window is obscured by another window, the
part of the note within the obscured region will not be printed.
(If a note is too long to fit within the Notepad window, the parts
that are not within the window will be printed.)

The text that appears in the Title Bar for the Calculator window
does not match the text that appears in the Title Bar for the Workbench
screen when the Calculator window is selected.


Other Software
--------------
Whenever the Polyscope tool on the 1.0 Kaleidoscope disk is opened,
the message Closed WB OK" is sent to the serial port.

On an Amiga with only 256K bytes of memory, the following steps
should be followed when opening Textcraft, Graphicraft, Amiga Basic,
or ABasiC from the Workbench:
   1. Open the drawer containing the tool.
   2. Drag the icon for the tool out of the drawer into the Workbench
      backdrop window.
   3. Close all windows.
   4. Open the tool.

When Textcraft is opened, the default margins are taken from
Preferences.  Margins set within Textcraft cannot be outside these
default margins.  For this reason, it is best to set the margins in
Preferences to 1 and 80 when using Textcraft to allow the greatest
possible range of margin settings within Textcraft.

Icon Editor
-----------
The Icon Editor does not verify that the type of the icon you
are writing out matches the type of the icon in the .info file you
are overwriting.  In particular, you should be careful not to overwrite
the Trashcan icon with other than an icon of type Garbage.

ED
---
ED fails if keys are typed while it is starting up.

Demos
-----
There are three problems with the demonstrations on release 1.0
of the Dealer's Workbench Demos disk:
     A smaller window appears inside a larger window when any of the
     demonstrations in the Pictures drawer is opened. When used with
     1.1 Kickstart disk, these smaller windows have a second Title Bar.

     Many of the demonstrations do not work when expansion memory (that
     is, memory connected to the Amiga's expansion bus) is added to an
     Amiga.

     The Molly program loses 10K bytes each time it is run.

New demonstrations will be developed that work properly with both
Release 1.1 of the system software and with expansion memory. These
demonstrations will be released on a new 1.1 Dealer's Workbench Demos disk.